Repository navigation
Release 0.3.0 - #13
Merged
Merged
Conversation
- Version 0.3.0: `cookies` and `headers` in the config, sent only to the site at baseUrl, for pinning A/B variants and reaching protected or signed-in pages (#12). - README: the status line no longer names a version that goes stale.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
cookiesandheadersin the config, sent only to the site atbaseUrl, for pinning A/B variants and reaching protected or signed-in pages (Send cookies and headers to your site #12).48 tests pass and
tsc --noEmitis clean locally.After merging: publish a GitHub release tagged
v0.3.0onmain, then approve the staged version on npmjs.com (RELEASING.md).